User

After I use the oem fob to start the car, the fob stops working. I cannot unlock or lock, til I hit the brake pedal to turn the rs off. Then I can use the fob again. 2020 kia optima key to start with t-harness. Believe it's in the firmware some option I dont have turned on or ??

Need to know where to hook up my duel shock , and siren on evo one wire to wire. Guide 88581 also going to use compustar 901 remote. I believe I only have to swap the rx/tx wire.

I have a kia optima 2020 key to start. Theres nothing for this vehicle....... only push to start and mine is key to start.

Wiring evo one in via wire to wire as theres more information on fortin, then I was going to use the d2d port from the evo one to the viper 5806v. Believe it's the red port on the viper and the 4 pin black on the evo. Can someone provide a ebay link to the part needed. Theres so many variations.

I need to know where the trunk release wire is and color . Assuming it does not work through the d2d , then I will need to hook it up to the viper to get the release button on viper fob to release trunk on my 2009 altima coupe push to start.

Evo,all w/thar-nis1 t harness, oem remote, standalone. Green wires are for lock n unlock. Where is siren wire ?

I'm not a Fortin rep but someone might find this useful -- I struggled with making these types of Compustar remotes work with the EVO-ONE. There are a few reports here of success with these remotes, and I had to do alot of experimentation to get satisfactory results, because these reports were somewhat vague and didn't cite which Firmware revisions were used when these observations were made. I can report that Firmware 7.1.24 (latest as of this thread) allows full function of these remotes without any drama, with the exception of a missing "remote start ready" (engine icon) indicator, which to me isn't any type of deal-breaker considering the capabilities of these units. Temperature, voltage, trunk, remote valet, alarm paging, etc. all work. The Fortin documentation states that FW 7.0.96 must be flashed for (supported) Compustar remotes, but this FW level is not sufficient to get full function from the (unsupported) T11/T12 remotes. 7.0.96 - Couldn't program remotes with Mode 1 or Mode 5. 7.1.16 - Remotes programmed immediately on Mode 5 and function, but temperature and voltage status reported erroneous numbers. 7.1.24 - Remotes programmed immediately on Mode 5 and all functions appear to work, with the exception of the "ready" engine icon which indicates a remote start is possible. IMHO, might be an issue for manual-transmission vehicles. Remote start functions regardless. To get this remote to work, flash the EVO-ONE to 7.1.24, and program the remotes with Mode 5. That's it. ** IMPORTANT ** -- There's no LED or valet switch on the antenna, even though the plastic housing looks like these features are there. This seriously confused me. I was trying to press that plastic square over-and-over thinking this was a valet switch, but it's a cosmetic feature, and does nothing, and there's no LED. I had to pop the antenna open to confirm this. Just flash to 7.1.24 and follow the instructions in the Compustar document from Fortin to program the remotes using Mode 5.

Purchased the EVO-GM1 for my 2012 Chevrolet Cruze. Want to install it in standalone but need to purchase an RF Kit since my factory FOB want function after car is started. Looking at picking up the Compustar Prime G15 FR-1WG15-AM RF Kit. Can't anthing on the internet to figure out if this is compatible with the EVO-GM1. Thanks